USAir Flight 405

USAir Flight 405

The wreckage of USAir Flight 405 lies partially inverted in Flushing Bay, New York
Accident summary
Date 22 March 1992
Type Icing, improper deicing procedures, pilot error, unforeseen delays
Site LaGuardia Airport, United States
Passengers 47
Crew 4
Injuries 21
Fatalities 27 (25 passengers + 2 crew)
Survivors 24 (22 passengers + 2 crew)
Aircraft type Fokker F28
Operator USAir
Tail number N485US
Flight origin LaGuardia Airport
Destination Cleveland Hopkins International Airport

USAir Flight 405 was a regularly scheduled domestic passenger flight between LaGuardia Airport in New York City, and Cleveland, Ohio. On March 22, 1992, a USAir Fokker F28, registration N485US, flying the route, crashed in poor weather in a partially inverted position in Flushing Bay, New York, shortly after liftoff from LaGuardia.[1] The undercarriage lifted off from the runway; however, the airplane failed to gain lift, flying only several meters above the ground. The aircraft then veered off the runway and hit multiple obstructions before coming to rest in Flushing Bay, just beyond end of the runway. Of the 51 people on board, 27 were killed in the accident, including the captain and one of the cabin crew members.

The subsequent investigation revealed that due to pilot error, inadequate deicing procedures at LaGuardia, and several lengthy delays, a large amount of ice had accumulated on the wings and airframe. This ice disrupted airflow over the jet, increasing drag and reducing lift, which prevented the jet from lifting off the runway.[2] The National Transportation Safety Board (NTSB) concluded that the flight crew were unaware of the amount of ice that had built up after the jet was delayed by heavy ground traffic taxiing to the runway. The report also listed the fact that the aircraft had begun its takeoff rotation too early at a lower speed than was standard as a contributing factor to the accident.

Investigators also found that the deicing procedures at LaGuardia were substandard. While the jet encountered a delay of up to 35 minutes, they found that the deicing fluid that was being used at the airport, and by the majority of commercial airlines across the United States, was effective for only fifteen minutes. The accident led to a number of studies into the effect that ice has on aircraft, and several recommendations into prevention techniques.

Contents

Flight history

The jet involved in the accident was a Fokker F28 Series 4000 airplane manufactured in the Netherlands. A two-engine, medium-range jet, the Fokker F28 is designed for transporting up to 95 passengers. The particular jet involved in the accident was registered in the United States as N458US. It was first delivered to Piedmont Airlines in August 1986, and was acquired by USAir—now named US Airways—three years later in August 1989 when the two airlines merged. N458US had amassed a total of 12,462 flying hours at the time of the accident.[3]

The 44-year old pilot, Captain Wallace J. Majure II, who was fully qualified to pilot the F28 and four other commercial aircraft, had accumulated approximately 9,820 total flying hours, of which 2,200 hours were in the F28. Majure was initially hired as an F28 first officer by Piedmont Airlines in 1985. He was later reassigned to serve as a first officer and then a captain on a Boeing 737, but finally returned to an F28 captain because of company cutbacks.[4] The New York Times reported that:

Majure was a man who yearned to please his passengers, and if he made them happy then he also made his airline happy. He had often spoken to friends about how important it was for him to get travelers to their destinations on time and how proud he was of USAir's on-time record. All the same, he was also portrayed as a by-the-book, cautious pilot.[5]

The first officer, John J. Rachuba, age 30, was hired by Piedmont in 1989. At the time of the accident, company records indicate that he had accumulated approximately 4,507 flying hours, of which 29 hours were in the F28. Rachuba held a flight engineer certificate with ratings for turbojet-powered aircraft and an expired instructor certificate issued on August 16, 1987. He also held an Federal Aviation Administration (FAA) license for non-federal control towers. Previously, he had served as a flight engineer on Boeing 737s and Boeing 727s.[6]

Accident

Poor weather, deicing, taxiing delays

The aircraft took off from Jacksonville International Airport, Florida, several hours before the accident, although the departure from Jacksonville was delayed by poor weather over New York and the removal of the baggage of a passenger who decided not to board the jet.[7] The instrument approach landing was uneventful and the jet was not significantly delayed while in the air waiting to land, however congestion on the taxiways at LaGuardia delayed the arrival of the aircraft at the gate.[8]

One hour and six minutes behind schedule[8], the jet arrived at Gate B1, where the pilot advised a ground mechanic that his airplane was "good to go."[8] The flight crew then disembarked the jet to use facilities in the terminal. The poor weather did not improve as the jet was deiced with Type I fluid, a heated 50/50 water/glycol mixture.[8] Following the completion of this process, one of the two deicing trucks delayed the pushback of the jet when it experienced mechanical problems. The vehicle was immobilised for 20 minutes in such a position that it prevented the aircraft from taxiing to the runway following the flight crew's return.[8]

After the deicing truck was repaired, the pilot requested a second deicing, though the flight crew did not perform a walkaround of their airplane, and USAir procedures did not require them to do so. Following the second deicing, LaGuardia ground control granted Flight 405 permission to taxi to Runway 13. The flight crew completed the pre-flight checklist during the taxi.[9]

Engine anti-ice was turned on for the two engines during taxi. The captain announced to passengers that the flaps would remain up during takeoff[8], and they should not be worried seeing them in the retracted position.[5] He placed an empty coffee cup on the flap handle as a reminder of the position of the flaps[8], a procedure used by many flight crews.[9] The captain told the first officer they would use standard USAir contaminated runway procedures that included the use of 18 degrees flaps, and also decided that they would take off with a reduced V1 speed of 110 knots.[10][11]

Weather reports for LaGuardia showed that on the night of the accident, all taxiways were coated with a thin covering of snow. Runway 13 was also covered with a thin layer of wet snow, although it had been plowed, treated with urea and it had been sanded.[12][13][14]

The first officer described the snowfall as "not heavy, no large flakes."[8] He told authorities that snow was sliding off the jet and the nose of the airplane was coated in a watery layer.[8] He used a light positioned on the wing of his jet to check for signs of ice several times before they attempted to take off.[9] Neither he or the pilot saw any evidence of contamination on the wing or on the black strip and therefore decided against a third deicing.[15] He told investigators that he checked the wings "maybe 10 times, but at least 3."[9] He said that he did not consider the snowfall heavy, and he did not recall any wind blowing the snow.[8] The first officer stated that as they taxied, they looked back at the wings several times. Near the time of the takeoff, he said "looks good to me, black strip is clear."[9]

While taxiing, the flight discussed deicing procedures. The first officer suggested to the pilot that the aircraft ahead of them in the queue "might keep our wings clear for us." The pilot replied that "it can cause us to re-freeze too ... I don't want to be very close to him."[16] Later, the first officer remarked "look at all that stuff. What is that?" to which the pilot replied "sand I guess, urea sand."[17]

The pilot of a jet taxiing behind Flight 405, Northwest Airlines Flight 517, a Boeing 757, stated that he had a good view of the top of Flight 405's wing, and that there was just enough snow on the fuselage to "fuzzy" the USAir printing but that the wings appeared to be clear.[9] He believed that the snow had "all but stopped" and was more concerned about the amount of vehicular traffic, such as sweepers and ploughs, than he was about the snowfall.[9] The second officer of Trump Shuttle Flight 1541, which had landed around the time Flight 405 was taxiing, said their Boeing 727 had "picked up a lot of snow quickly during my post-landing walkaround, but by the finish it seemed to be more rain."[9] He described Flight 405 as a "fairly clean airplane." He said that he could not comment on clear ice, but that the wings and fuselage were clear of snow.[18]

The jet, already several hours behind schedule, then suffered further delays taxiing to the runway. The weather had created heavy ground traffic at LaGuardia, and it was reported that there were queues of aircraft waiting for permission for takeoff. Investigators estimated that the plane took between 25 and 45 minutes to taxi from the gate to the runway.

Crash

Following permission for takeoff from controllers, the flight crew initiated the takeoff procedure and the first officer made a callout of 80 knots, and, several seconds later, a V1 callout, followed shortly after by a VR callout. Approximately 2.2 seconds after the VR callout, the nose gear left the ground. The first officer described the takeoff as normal through the rotation. The final report read that "the first officer described the takeoff as normal through the rotation. He stated that no problem was evident with vibration, rate of acceleration, ambient noise, [or] directional control".[18] However, The New York Times reported that "several passengers sensed that [the airplane] was not going fast enough."[5]

The first officer said it was "just like we lost lift."[19] As the captain attempted to level the wings, the crew used right rudder to manoeuvre the aircraft back toward the ground and avoid the water below. The accident report found that "the first officer said that they seemed to agree that the airplane was not going to fly and that their control inputs were in unison."[19] Rachuba and Majure continued to try to hold the nose up to impact in a flat attitude, although Rachuba later stated that there were no "heavy control inputs."[19] The final report further noted that "first officer stated that he did not touch the power levers."[20] The first officer later told investigators that the flight crew's primary focus was to find a safe place to land.[5]

Just under five seconds after the undercarriage left the ground, the plane's left wing scraped against the asphalt for 110 feet and the stick shaker activated.[18] The crew received six stall warnings[18], before the jet began banking to the left, then to the right, and then to the left again[5], still only several meters above the ground. The aircraft struck two visual approach slope indicator posts, touched down again for approximately 100 feet, before lifting off again and striking an ILS beacon and a water pump house.[5][19]

The left wing then separated from the body of the airplane, before the fuselage impacted with the edge of Flushing Bay and came to rest in a partially inverted position.[19] Parts of the fuselage and cockpit were submerged in water.[21] Confusion, disorientation, or entrapment most likely caused the drowning of passengers who otherwise sustained only minor injuries and injuries that were not life threatening.[22][23][24] The final report read:

Prior to impact, passengers did not assume the brace position. When the airplane came to rest, many of the passengers in the forward portion of the cabin were upside down, others, who were upright were submerged in water over their heads. Some passengers tried to move from their seats while their seatbelts were still buckled, and other passengers had difficulty locating and releasing their seatbelt buckles because of disorientation. Following the accident, passengers reported fires in the forward left and aft portions of the airplane, including many small fires on the water. Passengers stated that they escaped through large holes in the cabin. The lead flight attendant and first officer escaped through a hole in the cabin floor near the flight attendant’s position. Several passengers reported assisting others out of the cabin and into the knee-deep water. Many of them walked in the water to the dike, climbed up the wall and over an embankment, and slid down a steep hill to the runway. Others were assisted out of the water by ground personnel.[25]

Rescue attempts, medical operation

The tower cab coordinator on duty at the time of the accident stated that he saw a fireball emanating from the crash site following the accident. Upon seeing the flames, he sounded an alarm, alerting the Port Authority of New York and New Jersey Police, who responded.[25] An investigation revealed that there were technical issues with an emergency telephone at LaGuardia, however it was found that these issues did not hinder the emergency response.

The Port Authority of New York and New Jersey Police Department initially sent four vehicles.[26] Personnel in these vehicles reported that snow and fog hampered their visibility while heading to the crash site, and they could not see the destroyed aircraft. However, one member of the fire crew observed people standing on top of a dike near the crash site. Police divers also entered the water following the crash, although they found no-one alive inside the jet or in the water.[26] The fire-fighters continued spraying the fire, and the incident commander estimated that they had the fire under control ten minutes after their arrival at the scene. The New York Times reported that:

The accident sent thick black smoke billowing above the airport as more than 200 emergency workers ... had to contend not only with blustery snow but the powerful icy current in Flushing Bay ... the tense drama of the rescue continued into the early hours, with fire-fighters and police officers in water up to their shoulders and helicopters shining spotlights on the wreckage and an ice-covered mound of earth at the end of the runway so slick the rescue workers needed metal ladders to walk across it.[27]

The NTSB report on the accident noted, but did not criticise the medical operation at the scene. It described how paramedics attended to those who were conscious with life threatening injuries, but did not make any attempts to resuscitate victims who appeared drowned or lacked vital signs because they believed that they could not be revived because they had succumbed to the cold salt water. It was estimated by the authorities who attended the scene of the crash that 15 ambulances responded to the accident site, all of which were used to transport the injured to hospitals, and that 40 additional ambulances were available near the site of the crash, but were not needed.[28][29][30]

The report described the emergency response as "effective and contributed to the survivability of the airplane's occupants. However, the response by the emergency medical services personnel was inadequately coordinated, and the ambulance response times to the hospitals were excessive."[31] They final report read:

... a basic principle of triage is to treat victims having the most life-threatening injuries first with available medical resources and to utilize limited medical personnel in a manner that will provide maximum effectiveness. However, the Safety Board is also aware that in recent years a number of victims of cold water drowning have been successfully resuscitated. They survived after periods of underwater, including sea water, as long as one hour or more. In view of these facts, the Safety Board believes that all emergency response organizations should review their emergency plans to include contingencies for applying cardiopulmonary resuscitation (CPR) techniques as soon as a sufficient number of trained personnel arrive to perform CPR, even during mass casualty/triage incidents, regardless of whether vital signs are present, especially if cold-water immersion/near drowning is involved and where traumatic injuries do not indicate death.[30]

Investigation

The NTSB sent a team to the crash site to investigate the accident.[32] They concluded that, unknown to the crew, ice had collected on the wings, which disrupted airflow and reduced lift.[2] The inquiry lasted just under one year.[33]

Buildup of ice

The investigators suggested multiple reasons why the jet was unable to gain lift, but the accident report states there was no evidence to suggest corrosion on the wings. The airplane's flight control systems was also examined and revealed no failure prior to impact. The report reads that "the evidence did not support improper wing configuration, airframe or system defects, or deployment of the speed brakes as reasons for the loss of aerodynamic efficiency." The investigators also stated that the takeoff roll of the jet was not abnormal. The board came to the conclusion that ice had built up on the wings, and this had contributed largely to the accident.[14]

When attempting to find out why ice was present on the wings of the jet, the board determined that the airplane had been properly cleared of ice and snow during the two deicing procedures at the gate. However, approximately 35 minutes elapsed between the second time that the aircraft was deiced and the initiation of takeoff during which the airplane was exposed to continuing precipitation in below freezing temperatures. The NTSB were unable to determine how much ice had built up on the wings following the second deicing, but considered it to be highly likely that "some contamination occurred in the 35 minutes following the second deicing and that this accumulation led to this accident."[34]

"The Safety Board views the evidence as conclusive that the primary factor in this accident was the reduced performance of the wing due to ice contamination. Therefore, the Safety Board evaluated the extent to which the decisions of, and procedures used by the flight crew could have contributed to the accident," read the final report.[34] Although, when the cockpit was examined, the engine anti-ice switch was found in the 'OFF' position, further investigations found that even slight pressure could move the switch, and the NTSB ruled this out as a contributing factor in the crash.[22] Following the accident, USAir sent out a maintenance directive ordering engine anti-ice switches to be changed on F28s so they would lock into a selected position.[35]

Investigators found that a flaw in the design of the F28's wings made them extremely vulnerable to ice buildup. Because of the angle of the wings, even a very small amount of ice could have devastating effects.[36] When the NTSB, in collaboration with Fokker, investigated the effect ice can have on an aircraft, they found that ice particles as small as 1-2mm of a density of one particle per square centimeter can cause a loss of lift of over 20%.[37] A document written by Fokker before the accident detailed the effect of ice on the wing of an F28 warned that an "uncontrollable roll" would begin even with a small amount of ice on the wings.[38][39]

Errors by the flight crew

Two images detailing the effect that ice can have on aircraft

The report found that the flight crew were aware that the poor weather was likely to cause ice buildup, however neither of them took any action to check the condition of the wing leading edge and upper surface. The aircraft was evaluated by ground crew and was deiced. After the mechanical failure of the deicing truck, the investigators reported that, as the captain requested another deice, there was an indication he was:

... concerned about the continuing exposure to precipitation, and the request was prudent and in accordance with USAir guidance. Following the second deicing, the flight crew was most likely satisfied that the airplane was free of adhering contamination. The flight crew was not aware of the exact delay that they would encounter before takeoff and their decision to leave the gate was reasonable. After taxiing, when it became evident that they would be delayed for a prolonged period, conversations between the crew showed that they were aware of and probably concerned about the risk of reaccumulating frozen contamination on the wing.[34]

They also found that USAir guidance and flight crew training was sufficient and should have alerted the flight crew to the risk of attempting a takeoff while they were unaware of the condition of the wing. USAir guidance to flight crews specifically stated that:

... it is the captain's responsibility to exercise caution prior to takeoff. If the elapsed time since deicing exceeds 20 minutes, careful examination of the surfaces should be conducted to detect the extent of accumulation [of ice] and to assure that the takeoff can be made safely and in compliance with existing [regulations].[40]

The final report read:

The Safety Board believes that the flight crew of Flight 405 should have taken more positive steps to assure a contamination-free wing, such as entering the cabin to look at the wing from a closer range. Although the Safety Board acknowledges that the detection of minimal amounts of contamination, sufficient to cause aerodynamic performance problems, is difficult and may not be possible without a tactile inspection, an observation from the cabin would have improved the chance of seeing some contamination and might have prompted the flight crew to return to the gate. The Safety Board believes that the flight crew’s failure to take such precautions and the decision to attempt takeoff while unsure of wing cleanliness led to this accident and is a cause of it.[41]

In a television interview, one of the NTSB investigators suggested that "the captain was faced with quite a problem. If he wanted to be deiced a third time, he would have had to get out of the line [of jets waiting to take off] and taxi all the way back to the parking area and meet up with a deicing truck again. That would have put him very, very late and it may have even caused the cancellation of the flight."[36]

The NTSB carried out tests to discover why the first officer was unable to see the ice buildup on the wing of the jet. When the sliding window of the cockpit was fully open, the first officer would have been able to see the outer eighty percent of the wing, including the black strip used to contrast the white surface of the wing so the flight crew can search for a build up of ice. When the sliding window was shut, as it was in the accident,[42] it would be difficult to make out any details of the wing, and the black strip would have been distorted by the glass. They also found that the ice light made little difference to how much the first officer would have been able to see.[43][44]

The investigators also requested that Fokker conduct a study of the effects of ice contamination and pilot technique on the F28 aircraft. The NTSB evaluated the data from the tests and found that the pilot initiated the rotation five knots earlier at 119 knots instead of the proper rotation speed of 124 knots. The data from Fokker was correlated with the cockpit voice recording and confirmed that the first officer called a rotation speed of 113 knots but the captain did not rotate until 119 knots. It was never established why the rotation was called and initiated earlier than was standard.[45]

Deicing procedures at LaGuardia

Investigators also focused on deicing practices at LaGuardia. They found that the airport was using only Type I deicing fluid, not Type II. Type I fluids are used for the actual deicing of the jet, while Type II fluids are used for preventing buildup of ice. At the time of the accident, LaGuardia had prohibited the use of Type II deicing fluid because tests suggested that if it fell onto runways it reduced friction. Investigators noted the change had been made because of LaGuardia's shorter runways and the fact that if an aircraft left the vicinity of the runway, it would come to rest in the cold water surrounding Runway 13. The accident report, however, criticised the fact that the majority of the airplane operators in the United States relied only upon Type I fluids for protection, and they do not use Type II.[45][46] The board stated that tests have shown that both Type I and Type II fluids do flow off the wings of a treated airplane in significant amounts during the initial takeoff ground run. The NTSB stated:

There are a number of views on the potential uses of Type I and II fluids. The use of Type I fluid raises concern because its holdover time is shorter than the holdover time for Type II fluid under certain conditions. Both fluids are under scrutiny for their environmental impacts, and it is uncertain if Type II fluid diminishes the runway coefficient of friction since the fluid rolls off the airplane during the takeoff roll. Also, the use of either type fluid may result in a temporary degradation in the airplane's aerodynamic performance, a reduced stall margin, and an increase in drag.[47]

Safety card errors

While it was not named as a cause of the accident, investigators also found that the passenger safety briefing cards in the airplane showed two types of galley service doors. However, only one door is installed on a particular F28 model at any one time. The examination also showed that the safety card did not show how to operate either of the two types of galley service doors in the emergency mode if the normal opening mode failed.[48] However, the final report stated that this "did not contribute to the fatalities in the accident."[31]

Conclusion

The final report, published by the NTSB, cited the probable cause of the accident to be:

... the failure of the airline industry and the Federal Aviation Administration to provide flight crews with procedures, requirements, and criteria compatible with departure delays in conditions conducive to airframe icing and the decision by the flight crew to take off without positive assurance that the airplane's wings were free of ice accumulation after 35 minutes of exposure to precipitation following de-icing. The ice contamination on the wings resulted in an aerodynamic stall and loss of control after lift-off. Contributing to the cause of the accident were the inappropriate procedures used by, and inadequate coordination between, the flight crew that led to a takeoff rotation at a lower than prescribed air speed.[2]

Aftermath

NTSB recommendations

The NTSB made several recommendations to the FAA, including requiring that "flight crew members and appropriate ground personnel responsible for the inspection of transport-category airplanes for wing contamination receive specific periodic training that will illustrate what contamination looks like and feels like on a wing and the amount of contamination that is detectable under different light conditions".[49] They also ordered "airlines to establish a way to inform fight crews of the type of [deicing] fluid and mixture used, the current moisture accumulation rate, and the available holdover time.”[50]

With regard to the obstructions that the airplane collided with during the accident sequence, the NTSB ordered the modification or replacement of “all pump houses adjacent to Runway 13/31 so that they are not obstructions to airplanes”.[50] They also ordered a study on the “feasibility of building a frangible ILS antenna array for LaGuardia Airport”[51] Further, they ordered a review of Fokker F28-4000 passenger safety briefing cards "to ensure that they clearly and accurately depict the operation of the two types of forward cabin doors in both their normal and emergency modes and that they describe clearly and accurately how to remove the overwing emergency exit and cover."[50][51]

Dryden report allegations

The crash was featured on National Geographic Channel in an episode of the television program Mayday (Air Crash Investigation/Air Emergency) entitled Snowbound, where the accident was compared with Air Ontario Flight 1363, which crashed in Dryden, Ontario, after the crew did not deice their jet. The program opened by saying that Canadian investigators were "stunned" to hear of the accident, as it mirrored the Air Ontario flight which had occurred three years earlier.[36]

The report on the crash in Dryden criticised approaches to deicing. It made several points, including recommending the use of Type II deicing fluid was rather than Type I, deicing trucks near the runway rather than at the gate, and that the crew should inspect their wings not only from the cockpit, but also the cabin. The report concluded that competitive pressures caused by commercial deregulation cut into safety standards and that many of the industry’s sloppy practices and questionable procedures were placing pilots in difficult situations.[52]

The Honourable Virgil P. Moshansky, who investigated the crash in Dryden and wrote the report, appeared in the documentary, alleging that if the recommendations in his report had been followed, the USAir accident could have been prevented. Moshansky told the documentary that his report "probably sat on somebody's [at the FAA] desk." He said "when I first heard about it I thought, my God, it's Dryden all over again ... certainly if they had followed the recommendations in my report, the F28 crash at LaGuardia could have been averted."[36]

Another investigator into the Air Ontario accident told the documentary that "after all of this work [investigating the Dryden crash], after all of the efforts, to see it happen again was extremely frustrating."[36] The documentary focused largely on these allegations, while also reconstructing the Air Ontario flight and the USAir flight. However, it was reported that the FAA refuted Moshansky's allegations, and they claim that they never received his report.[36]

International Conference on Airplane Ground Deicing

Following the crash of Flight 405 and the Air Ontario accident in Dryden, the FAA began to research methods of improving deicing practices at airports to minimise the number of accidents caused by a buildup of ice.[53][54]

Described by the FAA as a “sharply focused effort”, experts convened on May 28 and May 29, 1992, in Reston, Virginia for the International Conference on Ground Deicing. At the conference, industry methods were discussed and agreed upon for actions that should be taken in the long term and short term. A report on the conference by the FAA read:

A better understanding of airplane ground deicing and anti-icing issues is a crucial prerequisite to the implementation of feasible and effective safety improvements. To achieve this goal, the FAA sponsored a conference at which the international aviation community could exchange thoughts and offer recommendation on a variety of issues concerning safe winter operations. [At the conference] more than 750 participants discussed the problems posed by aircraft deicing and examined possible solutions.[55]

It was reported that discussions over different types of deicing fluid were discussed, along with different deicing equipment and techniques. They also found that the pilot in command was the ultimate authority for take off decisions, but that all operators had to provide proper training and criteria to follow in order for the pilot in command to base a proper decision.

The conference concluded with an amendment to FAA regulations which air carriers operated under. The new regulations stated that airlines should put in place FAA-approved ground deicing or anti-icing procedures anytime weather conditions of ice, snow or frost prevailed. The new rules went into effect on November 1, 1992.[56]

Developments in deicing

In the years that followed the accident, airlines started using Type IV deicing fluid, which is more effective than both Type I and Type II fluids. Type IV fluids stick to aircraft for up to two hours.[36][57] Chicago O'Hare International Airport was the first to introduce deicing facilities at the runway, something which has now become commonplace.[36]

Aircraft themselves now have more sophisticated deicing systems that can be used on the ground and in the air. Many modern civil fixed wing transport aircraft, for example the Boeing 737, use anti-ice systems on the leading edge of wings, engine inlets and air data probes using warm air. This is bled from engines and is ducted into a cavity beneath the surface to be anti-iced. The warm air heats the surface up to a few degrees above zero, preventing ice from forming. The system may operate autonomously, switching on and off as the aircraft enters and leaves icing conditions. [58]

Ground deicing technologies are also developing, and a newer technology is infrared deicing. This is the transmission of energy by means of electromagnetic waves or rays. Infrared is invisible and travels in straight lines from the heat source to surfaces and objects without significantly heating the space (air) it passes through. When infrared waves strike an object, they release their energy as heat. This heat is either absorbed or reflected by the cooler surface. Infrared energy is continually exchanged between "hot" and "cold" surfaces until all surfaces have reached the same temperature (equilibrium). The colder the surfaces, the more effective the infrared transfer from the emitter. This heat transfer mechanism is substantially faster than conventional heat transfer modes used by conventional deicing (convection and conduction) due to the cooling effect of the air on the deicing fluid spray.[59][60]

Aircraft deicing vehicles have also improved since the accident, usually consisting of a large tanker truck, containing the concentrated de-icing fluid, with a water feed to dilute the fluid according to the ambient temperature. The vehicle also normally has a cherry picker crane, allowing the operator to spray the entire aircraft in as little time as possible; an entire Boeing 737 can be treated in under 10 minutes by a single de-icing vehicle.[61] Airport runways are also deiced by sprayers fitted with long spraying arms. These arms are wide enough to cross the entire runway, and allow de-icing of the entire airstrip to take place in a single pass, reducing the length of time that the runway is unavailable.

See also

New York City portal
Aviation portal

Similar accidents

References

  1. ^ "Accident description at the ASN". Aviation Safety Network. 11 March 2008. http://aviation-safety.net/database/record.php?id=19920322-1. Retrieved 16 July 2010. 
  2. ^ a b c National Transportation Safety Board (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 77. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=85. Retrieved 15 July 2010. 
  3. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 86. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=93. Retrieved 15 July 2010. 
  4. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 84. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=91. Retrieved 15 July 2010. 
  5. ^ a b c d e f Kleinfield, N. R. (29 March 2010). "The Ordinary Turned to Instant Horror for All Aboard USAir's Flight 405". The New York Times. http://www.nytimes.com/1992/03/29/nyregion/the-ordinary-turned-to-instant-horror-for-all-aboard-usair-s-flight-405.html?pagewanted=3. Retrieved 15 July 2010. 
  6. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 85. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=92. Retrieved 15 July 2010. 
  7. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 1. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=9. Retrieved 15 July 2010. 
  8. ^ a b c d e f g h i j NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 2. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=10. Retrieved 15 July 2010. 
  9. ^ a b c d e f g h NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 3. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=11. Retrieved 15 July 2010. 
  10. ^ Lorch, Donatella (June 23, 1992). "Before Crash, USAir Pilot Spoke Uneasily of Removing Ice From Wings". The New York Times. http://www.nytimes.com/1992/06/23/nyregion/before-crash-usair-pilot-spoke-uneasily-of-removing-ice-from-wings.html. Retrieved 17 July 2010. 
  11. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 55. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=63. Retrieved 15 July 2010. 
  12. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 12. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=20. Retrieved 15 July 2010. 
  13. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 13. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=21. Retrieved 15 July 2010. 
  14. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 47. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=55. Retrieved 15 July 2010. 
  15. ^ Philips, Don (March 26, 1992). "Copilot of Fatal La Guardia USAir Flight Says He Saw No Ice at Takeoff". The Washington Post. http://www.highbeam.com/doc/1P2-997441.html. Retrieved 17 July 2010. 
  16. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 92. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=99. Retrieved 15 July 2010. 
  17. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 98. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=105. Retrieved 15 July 2010. 
  18. ^ a b c d NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 4. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=12. Retrieved 15 July 2010. 
  19. ^ a b c d e NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 6. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=14. Retrieved 15 July 2010. 
  20. ^ Malnic, Eric; Goldman, John (23 March 1992). "Jet Crash Kills 20 in N.Y. Snowstorm : Disaster: The USAir commuter jet skids into Flushing Bay after trying to take off at La Guardia with 47 passengers, 4 crew members. Dozens are hurt.". Los Angeles Times. http://articles.latimes.com/1992-03-23/news/mn-3133_1_flushing-bay. Retrieved 17 July 2010. 
  21. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 22. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=30. Retrieved 15 July 2010. 
  22. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 29. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=37. Retrieved 15 July 2010. 
  23. ^ Malnic, Eric (25 March 1992). "Drowning Claimed 18 Jet Crash Victims : Aviation: Many survived impact, but were strapped upside down in seats below water line as tide rose in Flushing Bay". Los Angeles Times. http://articles.latimes.com/1992-03-25/news/mn-4218_1_flushing-bay. Retrieved 17 July 2010. 
  24. ^ "The Queens Spin – Plane Crashes". Queenstribune.com. http://www.queenstribune.com/anniversary2003/planecrashes.htm. Retrieved 17 July 2010. 
  25. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 33. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=41. Retrieved 15 July 2010. 
  26. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 34. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=42. Retrieved 15 July 2010. 
  27. ^ Barron, James (23 March 1992). "At Least 19 Killed in Crash at Snowy La Guardia". The New York Times. http://www.nytimes.com/1992/03/23/nyregion/at-least-19-killed-in-crash-at-snowy-la-guardia.html. Retrieved 17 July 2010. 
  28. ^ Mitchell, Alison (24 March 1992). "CRASH AT LA GUARDIA; The Tides of Flushing Bay Dictated the Pace of Rescue Efforts". The New York Times. http://www.nytimes.com/1992/03/24/nyregion/crash-la-guardia-tides-flushing-bay-dictated-pace-rescue-efforts.html. Retrieved 17 July 2010. 
  29. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 72. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=80. Retrieved 15 July 2010. 
  30. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 73. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=81. Retrieved 15 July 2010. 
  31. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 76. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=84. Retrieved 15 July 2010. 
  32. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 83. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=90. Retrieved 15 July 2010. 
  33. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 81. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=89. Retrieved 15 July 2010. 
  34. ^ a b c NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 53. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=61. Retrieved 15 July 2010. 
  35. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 36. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=38. Retrieved 15 July 2010. 
  36. ^ a b c d e f g h "Snowbound", Mayday, First aired 12 April 2010, National Geographic Channel
  37. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 75. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=83. Retrieved 15 July 2010. 
  38. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 49. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=57. Retrieved 15 July 2010. 
  39. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 50. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=58. Retrieved 15 July 2010. 
  40. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 42. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=50. Retrieved 15 July 2010. 
  41. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 54. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=62. Retrieved 15 July 2010. 
  42. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 26. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=34. Retrieved 15 July 2010. 
  43. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 40. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=48. Retrieved 15 July 2010. 
  44. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 41. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=49. Retrieved 15 July 2010. 
  45. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 56. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=64. Retrieved 15 July 2010. 
  46. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 65. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=73. Retrieved 15 July 2010. 
  47. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 64. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=72. Retrieved 15 July 2010. 
  48. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 70. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=78. Retrieved 15 July 2010. 
  49. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 78. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=86. Retrieved 15 July 2010. 
  50. ^ a b c NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 79. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=87. Retrieved 15 July 2010. 
  51. ^ a b NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 80. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=88. Retrieved 15 July 2010. 
  52. ^ Farnsworth, Clyde H. (27 March 1992). "Canadian Judge Calls Air Crash Avoidable". The New York Times. http://www.nytimes.com/1992/03/27/nyregion/canadian-judge-calls-air-crash-avoidable.html?pagewanted=all. Retrieved 17 July 2010. 
  53. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 61. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=69. Retrieved 15 July 2010. 
  54. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 62. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=70. Retrieved 15 July 2010. 
  55. ^ "Report of the FAA International Conference on Airplane Ground Deicing Held in Reston, Virginia on May 28–29, 1992 – Storming Media". Stormingmedia.us. 22 March 1992. http://www.stormingmedia.us/71/7163/A716362.html. Retrieved 17 July 2010. 
  56. ^ NTSB (March 1993). Washington D.C. 20594 – Aircraft Accident Report: USAir Flight 405. p. 44. http://libraryonline.erau.edu/online-full-text/ntsb/aircraft-accident-reports/AAR93-02.pdf#page=52. Retrieved 15 July 2010. 
  57. ^ A. Stefl, Barbara; F. George, Kathleen (4 December 2000). "Abstract : Antifreezes and Deicing Fluids : Kirk�Othmer Encyclopedia of Chemical Technology : Wiley InterScience". Kirk�Othmer Encyclopedia of Chemical Technology. http://mrw.interscience.wiley.com/emrw/9780471238966/kirk/article/antistef.a01/current/abstract. Retrieved 16 July 2010. 
  58. ^ Brady, Chris (2010). The Boeing 737 Technical Guide. 
  59. ^ White, Jim (18 May 2009). "Infrared Aircraft De-Icing". Airporttech.tc.faa.gov. http://www.airporttech.tc.faa.gov/safety/infrared.asp. Retrieved 15 July 2010. 
  60. ^ McCormick, Carroll. "Infrared Deicing: Giving glycol a run for its money". Wings Magazine. http://www.wingsmagazine.com/content/view/1325/38/. Retrieved 15 July 2010. 
  61. ^ "Winter service team at Dresden Airport ready for the cold season". Dresden Airport. 29 October 2004. http://www.dresden-airport.de/en/struktur/presse/pressemitteilungen/pmDetail.html?id=385. Retrieved 15 July 2010. 

 This article incorporates public domain material from websites or documents of the National Transportation Safety Board.

External links